InfoMagic Internet Tools 1995 April/Internet Tools.iso/dos_win/winsock/maillist/94-02.Z/94-02/text0102.txt

Text File | 1994-02-28 | 36.2 KB | 950 lines

I finally got the program working but..
I can't seem to connect to anyone. A friend set up his computer with wintalk
and I entered his email address in the talk box. When I press enter the talk
screen comes up(split window) and the message line says: checking for
invitation on caller's machine and then switches to: resending request.
Nothing else happens.
What am I doing wrong??
Thanks
************************************************
>From the Plant Genetics Lab at the U of M.

************************************************
From [e-mail] Wed Feb  9 20:39:10 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA22053; Wed, 9 Feb 1994 17:36:59 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA27890; Wed, 9 Feb 1994 17:08:42 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: 9 Feb 1994 20:39:10 GMT
From: [e-mail] (Michael Landman)
Message-Id: <[e-mail]>
Organization: Cabletron Systems, Inc.
Sender: ses
References: <[e-mail]>
Reply-To: [e-mail]
Subject: Re: Is there a newer pdipx available?

In article <[e-mail]>, [e-mail] (Richie L C TEH) writes:
|> Hi,
|>
|>     I have a problem running winqvtnet and windows for workgroups together.
|> If I were to use pdipx to start up, and execute winqvt, it seems to work (i.e
|> pop up a windows and prompt for login etc), but I can't find other workgroups
|> users if I try to do a chat or send a message. On the other hand, if I start
|> up my network using Novell's ipx, the reverse works, i.e. workgroups function
|> works, but qvt doesn't. HELP!!!!
|>
|>                         Richie
|>
|> --
|> Richie   ( that's me....)
|>

    Are you sure that you're using Novell's IPX? WFWG used to set up
its *own* ipx (msipx.sys & .com) for WFWG, because WFWG will only work
through an NDIS driver.

    If you are setting up ODI, and WFWG knows about it, it will add
ODINSUP (NDIS support for ODI) which is a shim which passes on NDIS calls
to the ODI driver.

    If msipx.sys & .com is what *works* for you, then WFWG is set
up to run under NDIS directly, and any other IPX will not work. To run
both of them concurrently, + Winsock, you could use your network card's
ODI driver, set up WFWG to use IPXODI (which will set up ODINSUP), then
use ODIPKT, a public domain shim that passes packet driver calls
to the ODI driver, which should work with winpkt or whatever winsock
driver you are using.



--
*********************************
* My opinions, not Cabletron's. *
*Stupid People Shouldn't Breathe*
*      [e-mail]        *
*********************************
From [e-mail] Wed Feb  9 12:40:45 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA26719; Wed, 9 Feb 1994 18:07:01 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA16649; Wed, 9 Feb 1994 17:49:17 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: 9 Feb 1994 17:40:45 -0500
From: [e-mail] (Glen Daniels)
Message-Id: <2jbopd$[e-mail]>
Organization: ELF Communications
Sender: ses
References: <[e-mail]>
Subject: Re: Problem with Wintalk / GENERAL WINTALK ISSUES

[e-mail] (Jim Blatta) writes:
>I can't get wintalk to work! Every time I start it up I get an error box
>which says:
>               Couldn't get OTALK socket
>                   Error #10055
>If anyone can help, many thanks.
>************************************************
>From the Plant Genetics Lab at the U of M.
>
>************************************************

To Jim:

What winsock are you using?  It's probably not configured for enough
UDP descriptors (you'll want at least four or five available for
WinTalk).

General WinTalk issues:

A bunch of folks reported problems with Trumpet winsock (GPF in
WINSOCK.DLL).  I cannot reproduce this problem here yet, but in at
least a couple of cases, upgrading to the 1.0A version of Trumpet
solved the problem.

There is also a known problem with PC-NFS (error #10050 receiving from
the talk daemon), which I *can* reproduce, but do not understand (the
error means "net down", which doesn't seem to be the case) - I'm on
the horn with SunSelect about it, and I'll let you know when it's
fixed or worked around.

WinTalk version 1.1 should be ready for release soon, after I track
down a couple more strange winsock-related bugs and finish adding
features.  As per usual, I'll post when it's ready.  New features in
v1.1:

* Text color selection
* Remembers "from" usernames even if they're not configured local unames
* Configurable remote "auto-wrap" for talking to Unix terminals
* Remembers full sound pathname

Thanks for all the positive comments, folks!

--
        --Gub (Glen Daniels, ELF Communications)
    "Gotta go inside, back where it started;
       Back to the beginning, 'cause that's where my heart is."
From [e-mail] Wed Feb  9 18:07:05 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA26732; Wed, 9 Feb 1994 18:07:05 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA12402; Wed, 9 Feb 1994 18:04:27 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Wed, 9 Feb 1994 17:14:28
From: [e-mail] (Harry M. Kriz)
Message-Id: <[e-mail]>
Organization: Virginia Tech
Sender: ses
Subject: Windows & tcp/ip for internet access (revised 2/9/94)

                                     Revised:    February 9, 1994
                                                       Release 03

                             Original version:  November 15, 1993


--------------------------------------
WINDOWS AND TCP/IP FOR INTERNET ACCESS

Several internet usenet groups and bitnet listservs contain a
continuous stream of basic questions about accessing the internet
using tcp/ip applications under Microsoft Windows.  One can
hardly post an answer to a question before seeing the same
question posted again by another person trying to get started.
Unfortunately, information on this topic is still scattered and
not easily found by beginners no matter what their level of
computer expertise.

This document contains a summary description of some shareware
and public domain software that can be used with Windows to
access services on the internet.  The software can be used either
on a PC connected directly to an ethernet network, or on a PC
with access to a dial-up SLIP server.

Many readers will need to consult a network guru in order to find
out about access through a network connection or through a SLIP
server.  It may be helpful to pass along this information about
specific Windows applications when seeking advice about the
capabilities of your local systems.

This discussion is limited to freeware and shareware products
freely available over the internet through anonymous ftp.  I
provide IP addresses for the official distribution sites and for
some alternative sites.  Some products are also available via
Gopher.

For each application, I provide a brief outline of the
installation procedures.  I do this primarily to illustrate the
simplicity of using Windows for internet access.  For full
instructions, please be sure to read any text files included with
each package in order to complete the configuration and to learn
about the full capabilities of the software.

I have installed all the software described here for several of
my colleagues in the Virginia Tech Libraries.  With some practice
I have found that I can finish installing a complete suite of
tcp/ip applications in about half an hour.  Some individuals who
read the previous version of this document and obtained the
software indicated they were up and running in less than an hour.
They expressed their delight at the ease of networking with
Windows.


----------
DISCLAIMER

I am not an expert on anything.  I am just an enthusiastic
end-user of these products in my daily work.  Some of these
products are in alpha or beta versions at this writing.  Despite
this, most are as stable and reliable as any commercial
application I use.  I would guess from messages on usenet that
they are in use by thousands of users all over the world.  The
alpha and beta designations may arise from the fact that features
are still being added by the authors.  Indeed, some of these
products have gone through several releases in the past few
months as developers responded via the internet to feedback from
users who reported bugs or requested new features.

My technical experience with ethernet is limited to using a
simple packet driver interface to the hardware.  Thus, I have no
experience using these products on network operating systems such
as Novell or Windows for Workgroups.  However, the applications
software described here should run with any tcp/ip protocol stack
that offers winsock support.  If your local network does not
include winsock support, you should check with your vendor to
find out if winsock support is available.  For example, Microsoft
recently released an inexpensive, winsock-compliant, tcp/ip
package for Windows for Workgroups. The Trumpet Winsock package
includes instructions for installing its tcp/ip protocol stack
and winsock support over your existing network using a packet
driver shim.  Thus, users of Novell Netware who do not yet have
winsock support can make use of this software.


----------------
LIMITED WARRANTY

I personally have used all of the software described below on at
least two different machine configurations:

  1.) 50MHz 486DX, AMI BIOS, SMC ethernet card using a packet
      driver interface connected to the Virginia Tech ethernet.

  2.) 33MHz 386DX, DTK BIOS, connected to the Virginia Tech SLIP
      server through a BOCA 14.4Kb/s fax-modem.

I have used most of the client software both under the Trumpet
Winsock shareware tcp/ip package described below, and under FTP
Software's PC/TCP Network Software for DOS using the generic
driver ethdrv.exe over a packet driver.  (This commercial package
also supports Windows, but that's the name of the product).  For
use with PC/TCP version 2.2, you should obtain the latest version
of FTP Software's WINSOCK.DLL. This file is now available by
anonymous ftp from vax.ftp.com in directory /support/winsock
under the name winsock.exe (a self-extracting ZIP file).


-------
WINSOCK

"Winsock" is the buzzword that dominates discussion about tcp/ip
and Windows.  All of the software described here is based on the
winsock specification for Windows tcp/ip applications.  In order
to get these applications working, there are only a few things
that an end-user needs to know about winsock and how it supports
Windows applications.

In my layman's terminology, the term "Winsock" refers to a
technical specification that describes a standard interface
between a Windows tcp/ip application (such as a gopher client)
and the underlying tcp/ip protocol stack that takes care of
transporting data on a tcp/ip network such as the internet.
Thus, when I invoke a program like HGopher, it calls procedures
from the WINSOCK.DLL dynamic link library.  These procedures in
turn invoke procedures in the drivers supplied with the tcp/ip
protocol stack.  The tcp/ip drivers communicate with the
computer's ethernet card through the packet driver.  For serial
line communications, the tcp/ip drivers communicate with a SLIP
driver to enable network communications through the serial port.

The WINSOCK.DLL file is not a generic file that can be used on
any system.  Each vendor of a tcp/ip protocol stack supplies a
proprietary WINSOCK.DLL that works only with that vendor's tcp/ip
stack.

The advantage to the developer of a winsock compliant application
program is that the application will work with any vendor's
winsock implementation.  Thus, the developer of an application
such as a gopher client has to understand the winsock interface,
but he does not have to know the details of each vendor's tcp/ip
protocol stack in order to make his client application compatible
with that stack.  It is this aspect of the winsock standard that
has resulted in a blossoming of winsock compliant shareware
applications since the summer of 1993.

The winsock standard offers advantages to the end-user.  One
advantage is that several winsock applications can be used
simultaneously.  This is a marked improvement over packet driver
applications in which each application contains a built-in tcp/ip
stack.  Such applications cannot share the packet driver except
through the added complexity of a packet multiplexor such as
PKTMUX.  A second advantage to the user is that any winsock
compliant application will run with any vendor's tcp/ip protocol
stack and accompanying WINSOCK.DLL.  Unfortunately, some
commercial vendors of tcp/ip clients are not yet taking advantage
of winsock capabilities.  Within the past two months, my library
has acquired one tcp/ip client that requires dedicated access to
the packet driver, and a second client that will run only with
the tcp/ip protocol stack supplied by one particular vendor.  One
can hope that commercial vendors will make their applications
more usable and portable by creating winsock compliant versions
as soon as possible.


---------------------
SOFTWARE DESCRIPTIONS


***************
TRUMPET WINSOCK  (tcp/ip protocol stack and basic clients, )
                 (including telnet, ftp, ping, archie      )

Comment:  You need this package (or some other tcp/ip protocol
stack that supports winsock) before you can use any of the client
software described later.

Author:     Peter Tattam

Fee:        $20 shareware fee.

Version:    1.0 Revision A

File name:  twsk10a.zip (February 3, 1994)
                (includes the tcp/ip protocol stack)
            winapps.zip (November 30, 1993)
                (includes basic clients)

Available by anonymous ftp from:
  ftp.utas.edu.au in /pc/trumpet/winsock
or by Gopher from
  info.utas.edu.au under menu item UTas FTP Archive

Installation:

  1.) Create directory C:\TRUMPWSK and unzip WINSOCK.ZIP and
      WINAPPS.ZIP into this directory.

  2.) Install software drivers.

      Ethernet network:

      a.) Install packet driver for your ethernet card.
          The entry in my AUTOEXEC.BAT file is:

          C:\ETHERNET\8003PKDR.EXE /B:240 /R:D000 /I:10 /E:61

      b.) Install WINPKT.COM virtual packet driver included in
          WINSOCK.ZIP.  The entry in my AUTOEXEC.BAT file is:

          C:\TRUMPWSK\WINPKT.COM 0x61

      SLIP:

      No special drivers are needed because SLIP support is
      built into the Trumpet Winsock TCPMAN.EXE program.

  3.) In Program Manager, create a program group named Network.
      Use File Manager to drag and drop the EXE files in
      C:\TRUMPWSK into the Network program group.

  4.) Edit the PATH statement in AUTOEXEC.BAT to include
      C:\TRUMPWSK. This enables winsock applications to find
      WINSOCK.DLL when they are launched.

  5.) Reboot the computer and start Windows.

  6.) Launch TCPMAN from the Network program group.
      Select Setup on the menu bar. Enter your ip address,
      gateway address, and nameserver address. If you are using
      ethernet, enter the software interrupt used by the packet
      driver. If you are using SLIP, check the SLIP check box
      and enter the appropriate COM port number in the SLIP port
      box.  Exit from TCPMAN.  The file TRUMPWSK.INI will be
      created in the C:\TRUMPWSK directory.

  7.) Launch any winsock compliant application. TCPMAN.EXE will
      start automatically if it is not already running.  Several
      clients are included with the Trumpet Winsock, including
      TELW.EXE for telnet, FTPW.EXE for ftp, WINARCH.EXE for
      searching Archie databases, PINGW.EXE to ping another
      machine on the network, and HOPCHKW to trace the path
      through the internet used to reach a particular host.

Note:  The WINSOCK.DLL file for the Trumpet Winsock remains in
the C:\TRUMPWSK directory.  Some vendors may require that their
WINSOCK.DLL be copied to the C:\WINDOWS directory.  If you have
used software from another vendor, but now want to try the
Trumpet Winsock, be sure to remove the other vendor's WINSOCK.DLL
so that it will not interfere with the Trumpet Winsock
implementation.

Tip:  The WINARCH client for archie searching defaults to
searching archie.au.  You can access another archie server by
using a command line argument.  For instance, to use the archie
server run by AT&T, use the command line
winarch -archie=ds.internic.net.

SLIP usage:  Trumpet Winsock includes a simple dialing function.
You can connect to your SLIP server by manually issuing the
dialing commands. You can also write a simple script that will
dial and start your SLIP session automatically.  Some SLIP
servers do not allow the use of a permanently assigned IP address
for your use. In that case, the SLIP server assigns a temporary
IP address at the start of the session.  In this case you should
enter a dummy IP address (e.g. 0.0.0.0) in the TCPMAN.EXE Setup
dialog.  When your SLIP session starts, TCPMAN will use the
address assigned by the SLIP server.
     PITFALL:  After dialing with TCPMAN.EXE and establishing the
     SLIP session, you must press the <ESC> key to escape from
     dialing mode and to re-enable the SLIP function in
     TCPMAN.EXE.

If you want to dial your SLIP server automatically, but you do
not care to write your own dialing script for TCPMAN.EXE, a
utility named DIALER provides a convenient means of dialing the
phone and automatically starting the SLIP session.  DIALER can be
set up to automatically issue the commands and passwords needed
to start the SLIP session.  DIALER version 1.0d is available by
anonymous ftp from:

     ftp.demon.co.uk
     /pub/ibmpc/windows/utilities/dialexe.zip   (January 6, 1994)


*******
HGOPHER  (Gopher client)

Author:     Martyn Hampson

License:    Public domain. Mr. Hampson suggests you donate $10.00
            to your favorite charity if you like HGopher.

Version:    2.4a

File name:  hgopher2.4.zip    (January 25, 1994)
                              (yes, that is not a valid DOS name)
                              (You will have to change it to    )
                              (something else when you download )
                              (it                               )

Available by anonymous ftp from:
  lister.cc.ic.ac.uk in /pub/wingopher
or by Gopher from
  gopher.ic.ac.uk

Installation:
  1.) Create the directory C:\HGOPHER and unzip hgopher2.4.zip
      (under whatever name you saved it) into this directory.
  2.) Create a new program item in the Network program group for
      the program C:\HGOPHER\HGOPHER.EXE.
  3.) Launch HGopher.
  4.) Supply the addresses and other information in the dialog
      boxes for the menu selections OptionsGopherSetUp and
      OptionsNetworkSetUp. For some types of information
      distributed via gopher, you will need to configure the
      viewers using the OptionsViewers dialog box. For example,
      you need to tell HGopher which telnet client to use, and
      which program to use for viewing jpeg or gif image files.
      The HGOPHER.INI file and bookmark files are kept in the
      C:\HGOPHER directory.


*******************
TRUMPET FOR WINDOWS  (usenet news reader and POP mail client)

Comment:  To read usenet news, you need access to an NNTP (usenet
news) server. To use the mail functions, you need an account on a
POP mail server. (I have not tested the mail functions in this
application because I prefer to use PC Eudora for mail.)

Author:     Peter Tattam

Version:    1.0 Revision A

File name:  wtwsk10a.zip   (August 28, 1993)

Available by anonymous ftp from:
  ftp.utas.edu.au in /pc/trumpet/wintrump
or by Gopher from
  info.utas.edu.au

Installation:
  1.) Create the directory C:\WINTRUMP and unzip WTWSK10A.ZIP
      into this directory.
  2.) Create a new program item in the Network program group for
      the program C:\WINTRUMP\WT_WSK.EXE.
  3.) Launch the program.
  4.) Supply the address and other information in the dialog
      boxes for the menu selections FileSetup and
      FileNetworkSetup. NEWS.PRM and other configuration files
      will be created and stored in C:\WINTRUMP.


*********
PC EUDORA  (full featured mail client)

Comment:  You will need an account on a POP mail server to send
and receive mail at your PC. Qualcomm sells a commercial version
of Eudora for both Windows and the Macintosh.

Author:     Jeff Beckley and Jeff Gehlhaar

License:    Shareware version is free

Version:    Shareware: 1.4
            (Commercial:  2.0)

File name:  eudora14.exe  (December 16, 1993)
                          (self extracting archive file)

Available by anonymous ftp from:
  ftp.qualcomm.com in directory /pceudora/windows

Installation:
  1.) Copy the file EUDORA14.EXE to the directory C:\PCEUDORA.
  2.) Execute EUDORA14 from the DOS prompt to unarchive the
      program files.
  3.) Create a new program item in the Network program group for
      the program C:\PCEUDORA\WEUDORA.EXE.
  4.) Launch the program.
  5.) Select SpecialConfiguration from the menu bar and supply
      the required information.
  6.) Select SpecialSwitches and set characteristics as desired.
  7.) Create mailboxes and nicknames to taste.
  8.) The file EUDORA.INI and other configuration files will be
      created in the C:\PCEDUORA directory.


*******
WS_FTP    (ftp client)
WS_PING   (ping client)

Author:     John Junod

License:    Public domain

Version:    94.02.08     (WS_FTP)
            94.01.23     (WS_PING)

File names: ws_ftp.zip    (February 9, 1994)
            ws_ping.zip   (January 27, 1994)

Available by anonymous ftp from:
  ftp.usma.edu in /pub/msdos/winsock.files
  Those who want to experiment with a beta copy of a newer
  version of WS_FTP can download ws_ftp.zip.new from /pub/msdos.

Installation:
  1.) Create the directory C:\WS_.
  2.) Unzip WS_FTP.ZIP into this directory.
  3.) Unzip the file WS_PING.EXE from its ZIP file into this
      directory also.  (Full source code for WS_PING is included
      in the ZIP file with the name WSPI_SRC.ZIP. Source code
      for the current version of WS_FTP is not distributed.
      However, source code for the 93-12-05 version of WS_FTP
      can be downloaded under the name ws_ftp_s.zip.)
  4.) Create new program items in the Network program group for
      the programs C:\WS_\WS_FTP.EXE and C:\WS_\WS_PING.EXE.
  5.) Launch the programs.
  6.) The WS_FTP.INI file remains in the C:\WS_ directory. A
      file named WINSOCK.INI is created by WS_PING in the
      C:\WINDOWS directory.


***********
NCSA MOSAIC for Microsoft Windows   (World Wide Web browser)
                                    (and Gopher client     )

Comment:  An exquisite display of World Wide Web documents,
including full color graphics mixed in with text.  General
protection faults can be a problem while using this program, or
shortly after exiting from it.  On occasion it has caused Windows
to crash to DOS.  I make sure files in other applications have
been saved before launching Mosaic.

Author:     Chris Wilson and Jon Mittelhauser

License:    Free

Version:    2.0 alpha 1

File name:  wmos20a1.zip  (February 6, 1994)

Available by anonymous ftp from:
  ftp.ncsa.uiuc.edu in /PC/Mosaic

Installation:
  1.) Create the directory C:\MOSAIC and unzip WMOS20A1.ZIP into
      this directory.
  2.) Create a new program item in the Network program group for
      the program C:\MOSAIC\MOSAIC.EXE.
  3.) Copy the file MOSAIC.INI to C:\WINDOWS. (You can put
      MOSAIC.INI in a different directory if you use a DOS
      environment variable to point to the correct directory.)
  4.) Edit the INI file following instructions in the file
      INSTALL.TXT.
  5.) Launch the program.


*****
CELLO  (World Wide Web browser and Gopher client)

Comment:  This Web client has some features that complement those
in Mosaic, so it is well worth trying both clients. General
Protection faults remain a problem.  The listserv CELLO-L is busy
with messages about CELLO development and about shareware for
creating HTML documents.  Instructions for subscribing are
included in the Help file.

Author:     Thomas R. Bruce

License:    Free

Version:    0.9  alpha r9.2

File name:  cello.zip  (November 22, 1993)

Available by anonymous ftp from:
  fatty.law.cornell.edu in /pub/LII/Cello

Installation:
  1.) Create the directory C:\CELLO and unzip CELLO.ZIP into
      this directory.
  2.) Create a new program item in the Network program group for
      the program C:\CELLO\CELLO.EXE.
  3.) Launch the program.

Tip:  It is worth while to obtain the file cello.exe from
/pub/LII/Cello/prerel to get the very latest version that is
being frequently revised. Version 1.0 pre 3b became available on
February 8. Simply copy this newer cello.exe over the version you
installed from the CELLO.ZIP file.


*****
WFTPD  (FTP server)

Comment:  I had not imagined I would want or need to use my PC as
an FTP server.  However, I have found this product useful on a
couple of occasions to transfer files from an IBM mainframe to my
PC.  This is far easier than trying to FTP to the mainframe from
my PC.  Some colleagues new to Windows and networking are
beginning to find it useful in order to exchange files with their
colleagues elsewhere in the library building or elsewhere on
campus.

Author:     Alun Jones

License:    $15.00.  The unregistered shareware version displays
            a humorous message to anyone accessing the server
            that the owner is too cheap to pay the shareware
            fee.

Version:    1.8b

File name:  wftpd18b.zip  (December 17, 1993)

Available by anonymous ftp from:
  ftp.cica.indiana.edu in /pub/pc/win3/winsock

Installation:
  1.) Create the directory C:\WFTPD and unzip WFTPD18B.ZIP into
      this directory.
  2.) Create a new program item in the Network program group for
      the program C:\WFTPD\WFTPDU.EXE.
  3.) Launch the program.
  4.) Complete the information in the FileSecurity dialog box to
      establish security control using access passwords and
      restricted home directories for those you authorize to
      access your PC.  The file WFTPDU.INI will be created in
      the C:\WINDOWS directory. (The registered version is named
      WFTPDR.EXE. It uses WFTPDR.INI. After registering, it is
      simplest to rename the registered version to WFTPD.EXE and
      rename the WFTPDU.INI file to WFTPD.INI so as to preserve
      existing security settings.)


------
TELNET

The glaring deficiency in the winsock pantheon of internet
clients is the absence of a good stand-alone telnet client.  Here
is a brief description of some alternatives I have tried.


****
TELW

Comment:  TELW.EXE is included with the Trumpet Winsock package
in the WINAPPS.ZIP file.  It is the first client that shareware
users are likely to try.  It is a minimal client with no
configuration possibilities.  It can be useful at times as a
terminal/telnet viewer in HGopher.


**********
WinQVT/Net

Comment:  WinQVT/Net is an integrated package that includes
telnet, ftp, ftp server, mail, and news reader clients.  These
client applications are normally launched from a console window.
The telnet client is probably the best shareware winsock telnet
client available.  You can select terminal emulations and
customize the keyboard.  The resizable telnet window includes
scrollback and session logging.  A deficiency is that telnet
cannot be launched independently of the console window.  However,
if WinQVT/Net is already running, then an instance of the telnet
client can be launched from another application by using the
TNSTART.EXE program that comes with WinQVT/Net.  This makes it
possible to use this telnet client for such applications as the
terminal/telnet viewer in HGopher.

Author:     QPC Software

License:    There has been discussion in alt.winsock about the
            difficulty of getting any response to e-mail and fax
            messages from the author.  Paying the license fee
            may be difficult as a result.

Version:    3.96

File name:  qvtws396.zip

Available by anonymous ftp from:
  biochemistry.bioc.cwru.edu (closed to public 9-5 weekdays)
or by Gopher from
  biochemistry.cwru.edu


TRMPTEL
*******

Comment:  This is my favorite telnet client at the moment.  It
can be used as a viewer for terminal/telnet with HGopher or with
Mosaic and Cello.  It is a very early release of a client that
can be expected to become excellent in the near future.

Author:     Peter Tattam

License:    Free beta version

Version:    0.04

File name:  trmptel.exe  (January 31, 1994)

Available by anonymous ftp from:
   petros.psychol.utas.edu.au in /pub/trumpet/trmptel


***********
NCSA TELNET

Comment:  NCSA telnet is a standard in the DOS and Macintosh
environments.  The winsock client is under development.  A
spokesman for NCSA has posted messages to the internet saying
that the existing client was thrown together quickly, and it is
not supported.  A student has been hired to write a new version
of the client, but it was said he had to learn tcp/ip and Windows
programming.  I have not found this client useful, but others may
wish to experiment with it.  No doubt NCSA will produce an
excellent telnet client in the future.

License:    Free

Version:    beta 3

File name:  wintelb3.zip  (October 21, 1993)

Available by anonymous ftp from:
  ftp.ncsa.uiuc.edu in /PC/Telnet/windows


*******
QWS3270

Comment:  Telnet clients usually emulate a VT100 terminal or one
of its variations, the standard for connecting to a Unix host.
However, telneting to an IBM mainframe requires emulation of an
IBM 3270 terminal.  QWS3270 provides the necessary functionality.
I was especially pleased with the easily-configured 4 color
capability that makes it easier to distinguish protected,
unprotected, and highlighted text on a VM screen.

Author:     Jim Rymerson

License:    Free

Version:    2.5a

File name:  qws3270.zip  (January 31, 1994)

Available by anonymous ftp from:
  ftp.ccs.queensu.ca in /pub/msdos/tcpip


-------------------------------------
OTHER SOURCES FOR WINSOCK INFORMATION

Considerable information about winsock, along with some
application programs, is available at:

sunsite.unc.edu
in directory /pub/micro/pc-stuff/ms-windows/winsock

The anonymous ftp sites that I list as sources for programs are
the sites designated by the authors as their home sites.  These
sites will always have the latest version of the software.

Copies may usually be obtained by anonymous ftp from
ftp.cica.indiana.edu in /pub/pc/win3/winsock.  However, it is the
case that CICA will contain some versions that are out of date.
Check the directory /pub/pc/win3/uploads to see if a new version
was recently uploaded.  Dates on the files at CICA may disagree
with the dates on the files at the home sites.  Note that CICA is
the main internet site for Windows applications.  It is usually
busy, and you may have difficulty connecting.  There are several
other internet sites that provide mirror copies of the Windows
collection at CICA.  These are listed in the message displayed if
you are denied access to CICA.  The list of mirror sites is
included in the file README in the /pub/pc/win3 directory.  When
using CICA, it is helpful to download the file INDEX (ascii) or
INDEX.ZIP from /pub/pc/win3.  This file contains short
descriptions of each file in the collection.

The usenet groups alt.winsock and comp.protocols.tcp-ip.ibmpc
carry discussions of the winsock specification and winsock
compliant applications. Information about specific clients may be
found in groups devoted to that class of client.  For instance,
HGopher is discussed in alt.gopher and in
comp.infosystems.gopher.  The Bitnet listserv WIN3-L@UICVM
carries discussions about all topics relating to Windows,
including winsock applications.

A FAQ (Frequently Asked Questions) about tcp/ip on PC-compatible
computers written by Bernard D. Adoba is posted monthly on
comp.protocols.tcp-ip.ibmpc.  A copy can be obtained by anonymous
ftp from rtfm.mit.edu in directory
/pub/usenet-by-hierarchy/comp/protocols/tcp-ip/ibmpc.  It is also
available under the name ibmtcp.zip from netcom1.netcom.com in
directory /pub/mailcom/IBMTCP.

An introduction to SLIP is available by pointing your gopher
client at gopher.vt.edu. Look down the menus through
Experimental-file-system/nyman/whatslip.txt.

The latest version of this document is available by anonymous ftp
from nebula.lib.vt.edu in /pub/windows/winsock under the name
wtcpip**.zip.


================================================================
I thank each of you who sent me personal messages following the
posting of the first and subsequent versions of this document.
So far I have received e-mail from individuals on 6 continents.
I have not yet heard from anyone in Antarctica.  I am gratified
to have been able to help many of you, and I appreciate the
suggestions and information provided by others.  My efforts in
producing this document can be only a small and indirect
repayment of the debt I owe to those developers who produced the
software described here.

Please send error reports to me at the address below.  I would be
grateful for suggestions for improvements and additions to this
document.  Thanks again to everyone who replied to my beginner's
questions over the past few months.  I greatly appreciate your
patience, and your willingness to share your knowledge.
=================================================================

Harry M. Kriz
[e-mail]
University Libraries
Virginia Polytechnic Institute & State University
Blacksburg, VA   24061-0434

-----------------------------------------------------------------
Harry M. Kriz      [e-mail]
University Libraries
Virginia Polytechnic Institute & State University (Virginia Tech)
Blacksburg, VA   24061
From [e-mail] Wed Feb  9 07:08:00 1994
Received: from netmail2.microsoft.com by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA27291; Wed, 9 Feb 1994 18:09:46 -0500
Received:  by netmail2.microsoft.com (5.65/25-eef)
    id AA06184; Wed, 9 Feb 94 15:10:37 -0800
Received: by netmail2 using fxenixd 1.0 Wed, 09 Feb 94 15:10:36 PST
Message-Id: <9402092309.AA10838@itgmsm>
From: [e-mail]
To: [e-mail]
Subject: WSAT Info
Date: Wed, 09 Feb 94 15:08:00 PST
X-Mailer: Microsoft Mail V3.0




WSAT Users,

An updated WSAT is available at rhino.microsoft.com in the wsat directory.

This release contains NO new functionality.  It is provided primarily to
remove the timebomb on wsat.exe and has a few minor bug fixes that you folks
pointed out (in asu0.ts, bindt.tst, host.tst and writet1.tst) thrown in.

The following is the background/how-to provided at [e-mail].

enjoy,
     jim

 ----------------------------------------------------------------------------
 ------------------
Thank you for sending mail to [e-mail].

We are freely distributing the latest version of the tester and
scripts to winsock implementation developers for the purpose of
encouraging the highest quality winsock implementations and
maximizing appilcation interoperability.

It should be noted that wsat is intended for this purpose -- helping
developers whip their winsock implementations into shape -- and is
NOT useful for winsock application developers.  Nor is WSAT is a
good numerical benchmark.  The test reports results in terms of
"variations", which are simply a single item of winsock behavior that
I am trying to verify.  Some of these variations are critically
important -- their failure would break many applications -- while
many others might affect no applications at all.  In addition, the
variation failures many range from the catastrophic (a crash) to
trivial error code issues.  Hence, without knowledge of the specific
variation failing and the failures involved, a simple pass/fail
report from wsat gives only the grossest measure of winsock spec
compliance.

The latest version of the tester and scripts are on rhino.microsoft.com
via anonymous FTP.  Once logged on change to the wsat directory.
The distribution is contained in the form of a self-extracting archive,
wsat194.exe or as individual files in the distrib directory.

Please read the WSAT description/instructions in wsat.txt.  If you
encounter any problems running WSAT, or have feedback for improving
the tester or scripts, e-mail [e-mail].

best of luck with your winsock implementation,
    jim